Managing external feeds in an event-based computing system

ABSTRACT

At a cloud platform, a class of feed is received for an external feed corresponding to an information source, as are an instruction corresponding to a create operation for the external feed, and a dictionary input corresponding to parameters expected by the information source. The external feed produces a corresponding class of events. At the cloud platform, a handler is selected based on the received class of feed and the received create operation; the input dictionary is transferred to the handler; and the handler generates a unique destination to receive events for the class of events. The handler on the cloud platform generates a unique request to the information source to generate events of the class of feed to the unique destination and sends the request to the information source. Events generated from the information source responsive to the unique request are received at the unique destination.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional PatentApplication 62/298,194, filed 22 Feb. 2016, entitled Managing ExternalFeeds in an Event-Based Computing System, and also claims the benefit ofU.S. Provisional Patent Application 62/298,093, filed 22 Feb. 2016,entitled Language-Independent Program Composition using Containers. Thecomplete disclosures of U.S. Provisional Patent Application 62/298,194and U.S. Provisional Patent Application 62/298,093 are expresslyincorporated by reference herein in their entireties for all purposes.

BACKGROUND

The present invention relates to the electrical, electronic and computerarts, and, more particularly, to cloud programming models, runtimes andintegration, including, for example, application and integrationmiddleware and the like.

In the realm of event-based computing processing systems, a programmingmodel is provided whereby a user specifies a “handler” function, andregisters the handler to run in response to certain events that arise. Adistributed event-based system manages the delivery of events andmanagement of handler code, to ensure that handlers execute in responseto events.

Typically, event-based computing is employed to handle events that arisefrom some external source, called a “feed.” Examples of feeds includeprice quotes from an equity trading service, news bulletins from a newsaggregator, or notifications from a source code control system.

In order to use a feed, the feed must typically be configuredexternally. That is, there must be interaction with some managementservice from the feed provider, to select a certain stream of events andconfigure the service to send those events to the event-based computingsystem desired.

In this model, a user of an event-based computing system must interactwith a separate management system and interface for each feed the userdesires to consume. Since each feed management system is different, thisintroduces a burden on the user. See, e.g., Gero Mühl et al.,Distributed Event-Based Systems, Springer-Verlag Berlin Heidelberg 2006,expressly incorporated by reference herein in its entirety for allpurposes.

SUMMARY

Principles of the invention provide techniques for managing externalfeeds in an event-based computing system. In one aspect, an exemplarymethod includes the step of receiving, at a cloud platform, a class offeed for an external feed corresponding to an information source (theexternal feed to produce a corresponding class of events). Further stepsinclude receiving, at the cloud platform, an instruction correspondingto a create operation for the external feed; receiving, at the cloudplatform, a dictionary input corresponding to parameters expected by theinformation source; selecting, at the cloud platform, a handler based onthe received class of feed and the received create operation;transferring, to the handler on the cloud platform, the inputdictionary; generating, at the cloud platform, a unique destination toreceive events for the class of events; generating, by the handler onthe cloud platform, a unique request to the information source togenerate events of the class of feed to the unique destination; sending,by the handler on the cloud platform, the request to the informationsource; and receiving, at the unique destination, events generated fromthe information source responsive to the unique request.

As used herein, “facilitating” an action includes performing the action,making the action easier, helping to carry the action out, or causingthe action to be performed. Thus, by way of example and not limitation,instructions executing on one processor might facilitate an actioncarried out by instructions executing on a remote processor, by sendingappropriate data or commands to cause or aid the action to be performed.For the avoidance of doubt, where an actor facilitates an action byother than performing the action, the action is nevertheless performedby some entity or combination of entities.

One or more embodiments of the invention or elements thereof can beimplemented in the form of a computer program product including acomputer readable storage medium with computer usable program code forperforming the method steps indicated. Furthermore, one or moreembodiments of the invention or elements thereof can be implemented inthe form of a system (or apparatus) including a memory, and at least oneprocessor that is coupled to the memory and operative to performexemplary method steps. Yet further, in another aspect, one or moreembodiments of the invention or elements thereof can be implemented inthe form of means for carrying out one or more of the method stepsdescribed herein; the means can include (i) hardware module(s), (ii)software module(s) stored in a computer readable storage medium (ormultiple such media) and implemented on a hardware processor, or (iii) acombination of (i) and (ii); any of (i)-(iii) implement the specifictechniques set forth herein.

Techniques of the present invention can provide substantial beneficialtechnical effects. For example, one or more embodiments provide one ormore of:

end user can consume an external feed without needing to know details ofhow to manage same;

a feed management application programming interface (API) can beencapsulated as an event handler which responds to lifecycle events onthe feed, transparently to the end user;

feeds, encapsulated by lifecycle handlers, can be managed, organized,and queried like other event handlers.

These and other features and advantages of the present invention willbecome apparent from the following detailed description of illustrativeembodiments thereof, which is to be read in connection with theaccompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts a cloud computing environment according to an embodimentof the present invention;

FIG. 2 depicts abstraction model layers according to an embodiment ofthe present invention;

FIG. 3 is a block diagram of an exemplary event-based computing systemaccording to an embodiment of the present invention;

FIG. 4 is a custom feed example, according to an aspect of theinvention;

FIGS. 5 and 6 show logical architectures of a github feed service,according to aspects of the invention;

FIG. 7 shows aspects of a feed action, according to an aspect of theinvention; and

FIG. 8 depicts a computer system that may be useful in implementing oneor more aspects and/or elements of the invention, also representative ofa cloud computing node according to an embodiment of the presentinvention.

DETAILED DESCRIPTION

It is understood in advance that although this disclosure includes adetailed description on cloud computing, implementation of the teachingsrecited herein are not limited to a cloud computing environment. Rather,embodiments of the present invention are capable of being implemented inconjunction with any other type of computing environment now known orlater developed.

Cloud computing is a model of service delivery for enabling convenient,on-demand network access to a shared pool of configurable computingresources (e.g. networks, network bandwidth, servers, processing,memory, storage, applications, virtual machines, and services) that canbe rapidly provisioned and released with minimal management effort orinteraction with a provider of the service. This cloud model may includeat least five characteristics, at least three service models, and atleast four deployment models.

Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provisioncomputing capabilities, such as server time and network storage, asneeded automatically without requiring human interaction with theservice's provider.

Broad network access: capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, laptops, and PDAs).

Resource pooling: the provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according todemand. There is a sense of location independence in that the consumergenerally has no control or knowledge over the exact location of theprovided resources but may be able to specify location at a higher levelof abstraction (e.g., country, state, or datacenter).

Rapid elasticity: capabilities can be rapidly and elasticallyprovisioned, in some cases automatically, to quickly scale out andrapidly released to quickly scale in. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured service: cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth, and active user accounts). Resource usage can bemonitored, controlled, and reported providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices through athin client interface such as a web browser (e.g., web-based email). Theconsumer does not manage or control the underlying cloud infrastructureincluding network, servers, operating systems, storage, or evenindividual application capabilities, with the possible exception oflimited user-specific application configuration settings.

Platform as a Service (PaaS): the capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages and tools supported bythe provider. The consumer does not manage or control the underlyingcloud infrastructure including networks, servers, operating systems, orstorage, but has control over the deployed applications and possiblyapplication hosting environment configurations.

Infrastructure as a Service (IaaS): the capability provided to theconsumer is to provision processing, storage, networks, and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage,deployed applications, and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private cloud: the cloud infrastructure is operated solely for anorganization. It may be managed by the organization or a third party andmay exist on-premises or off-premises.

Community cloud: the cloud infrastructure is shared by severalorganizations and supports a specific community that has shared concerns(e.g., mission, security requirements, policy, and complianceconsiderations). It may be managed by the organizations or a third partyand may exist on-premises or off-premises.

Public cloud: the cloud infrastructure is made available to the generalpublic or a large industry group and is owned by an organization sellingcloud services.

Hybrid cloud: the cloud infrastructure is a composition of two or moreclouds (private, community, or public) that remain unique entities butare bound together by standardized or proprietary technology thatenables data and application portability (e.g., cloud bursting for loadbalancing between clouds).

A cloud computing environment is service oriented with a focus onstatelessness, low coupling, modularity, and semantic interoperability.At the heart of cloud computing is an infrastructure comprising anetwork of interconnected nodes.

Referring now to FIG. 1, illustrative cloud computing environment 50 isdepicted. As shown, cloud computing environment 50 includes one or morecloud computing nodes 10 with which local computing devices used bycloud consumers, such as, for example, personal digital assistant (PDA)or cellular telephone 54A, desktop computer 54B, laptop computer 54C,and/or automobile computer system 54N may communicate. Nodes 10 maycommunicate with one another. They may be grouped (not shown) physicallyor virtually, in one or more networks, such as Private, Community,Public, or Hybrid clouds as described hereinabove, or a combinationthereof. This allows cloud computing environment 50 to offerinfrastructure, platforms and/or software as services for which a cloudconsumer does not need to maintain resources on a local computingdevice. It is understood that the types of computing devices 54A-N shownin FIG. 1 are intended to be illustrative only and that computing nodes10 and cloud computing environment 50 can communicate with any type ofcomputerized device over any type of network and/or network addressableconnection (e.g., using a web browser).

Referring now to FIG. 2, a set of functional abstraction layers providedby cloud computing environment 50 (FIG. 1) is shown. It should beunderstood in advance that the components, layers, and functions shownin FIG. 2 are intended to be illustrative only and embodiments of theinvention are not limited thereto. As depicted, the following layers andcorresponding functions are provided:

Hardware and software layer 60 includes hardware and softwarecomponents. Examples of hardware components include: mainframes 61; RISC(Reduced Instruction Set Computer) architecture based servers 62;servers 63; blade servers 64; storage devices 65; and networks andnetworking components 66. In some embodiments, software componentsinclude network application server software 67 and database software 68.

Virtualization layer 70 provides an abstraction layer from which thefollowing examples of virtual entities may be provided: virtual servers71; virtual storage 72; virtual networks 73, including virtual privatenetworks; virtual applications and operating systems 74; and virtualclients 75.

In one example, management layer 80 may provide the functions describedbelow. Resource provisioning 81 provides dynamic procurement ofcomputing resources and other resources that are utilized to performtasks within the cloud computing environment. Metering and Pricing 82provide cost tracking as resources are utilized within the cloudcomputing environment, and billing or invoicing for consumption of theseresources. In one example, these resources may include applicationsoftware licenses. Security provides identity verification for cloudconsumers and tasks, as well as protection for data and other resources.User portal 83 provides access to the cloud computing environment forconsumers and system administrators. Service level management 84provides cloud computing resource allocation and management such thatrequired service levels are met. Service Level Agreement (SLA) planningand fulfillment 85 provide pre-arrangement for, and procurement of,cloud computing resources for which a future requirement is anticipatedin accordance with an SLA.

Workloads layer 90 provides examples of functionality for which thecloud computing environment may be utilized. Examples of workloads andfunctions which may be provided from this layer include: mapping andnavigation 91; software development and lifecycle management 92; virtualclassroom education delivery 93; data analytics processing 94;transaction processing 95; and software elements of an event-basedcomputing system 96, according to an aspect of the invention.

Note that while FIG. 2 shows servers, some embodiments of the inventionare implemented in a serverless fashion, as discussed herein.

As noted, in the realm of event-based computing processing systems, aprogramming model is provided whereby a user specifies a “handler”function, and registers the handler to run in response to certain eventsthat arise. A distributed event-based system manages the delivery ofevents and management of handler code, to ensure that handlers executein response to events.

Typically, event-based computing is employed to handle events that arisefrom some external source, called a “feed.” Examples of feeds includeprice quotes from an equity trading service, news bulletins from a newsaggregator, or notifications from a source code control system.

In order to use a feed, the feed must typically be configuredexternally. That is, there must be interaction with some managementservice from the feed provider, to select a certain stream of events andconfigure the service to send those events to the event-based computingsystem desired.

In this model, a user of an event-based computing system must interactwith a separate management system and interface for each feed the userdesires to consume. Since each feed management system is different, thisintroduces a burden on the user.

Referring now to FIG. 3, one or more embodiments advantageously allowthe event-based computing system 304 to present a unified managementinterface 306 for external feeds (e.g., FEED₁ 320-1, FEED₂ 320-2 . . .FEED_(N) 320-N; collectively 320). Because of the lack of standards forfeed management interfaces, current techniques have been unable toprovide a uniform interface to arbitrary disparate feed sources.

One or more embodiments provide techniques whereby an event-basedprocessing system can present a uniform interface to feed managementservices from arbitrary feed providers (e.g., INFORMATION SOURCE/FEEDPROVIDER₁ 318-1, INFORMATION SOURCE/FEED PROVIDER₂ 318-2 . . .INFORMATION SOURCE/FEED PROVIDER_(N) 318-N; collectively 318). Onesignificant aspect is that the system can represent key lifecycle eventsfor a feed as events managed by the system, and let the feed providersprovide event handlers that the system knows how to manage in thecontext of its event-based programming model.

One or more embodiments assume an event-based computing system where anyuser (e.g., end user 324 or one of the feed providers 318) can define a“handler” 312, which is a piece of code that runs in response to certainevents. Additionally, the system provides a mechanism to define a classof events based on some criterion. The simplest models are “topic-based”classes 308, where each event is tagged with a “topic,” and the topicdefines a class. Other models, such as “content-based” classes 310, arealso possible. Furthermore in this regard, a feed is a stream of events.If it is desired to associate an event handler with it, it isappropriate to specify which events are of interest. Reference is madeto the well-known model of publish-subscribe (“pub-sub”) computation. Intopic-based pub-sub, a user specifies interest in all messages with acertain topic (e.g., “food”), essentially via a tagging process (lookfor messages tagged “food”). Content-based pub-sub provides a richerlanguage for describing events of interest. For instance, rather thanmerely specifying interest in all messages tagged “food,” one couldindicate an interest in all events which are tagged “food” and whichoccurred between September and October near New York. Thus, in thecontent-based pub-sub model, besides merely expressing interest in thetag or topic of the message, the properties of the message itself(content) can be described. Embodiments of the invention can be usedwith topic-based approaches and/or content-based approaches. Purely forillustrative purposes, a non-limiting topic-based exemplary embodimentwill be described. However, given the teachings herein, the skilledartisan will also be enabled to implement content-based approaches.

One or more embodiments also assume that users can publish handlers 312visible and callable by other users. For example, one of the feedproviders 318 may publish a handler 312 that can be called by end user324 who wishes to consume a corresponding feed.

Consider now a non-limiting example of how to manage external feeds 320.

In one or more embodiments, the system 304 defines a small set of“lifecycle” events for each class 308 of feed 320. In one embodiment,the set of lifecycle events for a feed could be {CREATE, DELETE, PAUSE,RESUME}.

Next, the feed provider 318 defines a handler 312 for each of thelifecycle events associated for the feed provider's feed. Alternatively,the feed provider can provide a single handler which responds to thevarious lifecycle events as appropriate for each event. Since theevent-based computing system 304 allows arbitrary code as handlers, thefeed provider 318 can place arbitrary code as the handler 312 for eachlifecycle event. For the subsequent discussion, assume a separatehandler for each lifecycle event on a feed; however, the same principlesapply for the case of a single handler which can handle all events, andtakes the particular type of event as input.

Accordingly, the CREATE handler 312 for a feed can, for example,negotiate with a feed provider's service 318 via any arbitraryapplication programming interface (API) (e.g., API₁ 322-1, API₂ 322-2 .. . API_(N) 322-N; collectively, 322) to establish a feed of events, andarrange for these events to flow to the event-based computing service304. Similarly, the DELETE handler could negotiate with a feedprovider's service to destroy a feed of events, and PAUSE and UNPAUSEhandlers can negotiate with a feed provider's service to place the feedin an appropriate state.

Pertinent benefits to the user 324 in one or more embodiments include:

The user 324 need not worry about the details of how to create, delete,or otherwise manage a particular feed 320. Instead, the feed provider318 encapsulates the details in the handler 312 for a lifecycle event.The user 324 need only generate a CREATE event (or other lifecycleevent) with parameters as expected by the handler 312, and be confidentthat the feed is created as expected.

If the feed management API 322 changes, the changes can be encapsulatedin a change to the lifecycle handler 312—users 324 of the handler neednot know.

The feeds 320, as encapsulated by lifecycle handlers 312, can bemanaged, organized, and queried just like all the other event handlersin the system.

Furthermore, in one or more embodiments, the system can automaticallyhide some details relating to setting up integrations between feedproviders 318 and the event-based computing system 304. For example,suppose that the system uses topic-based event classes 308—the systemcan automatically pass the information relevant to a topic (e.g. URL,credentials, etc.) to the feed handler 312, without any participation byan end user 324.

Consider now one non-limiting example of how to employ an exemplaryembodiment of the invention; in particular, an example of an applicationthat can be built using an exemplary embodiment of the invention. Again,by way of review, one or more embodiments are directed to managingfeeds. Consider the GitHub web-based repository hosting service, whichis one non-limiting example of a service that could provide a feed whichpeople might be interested in. GitHub is a popular site that allowspeople to host their source code and manage development of their code.The user can instruct the GitHub site to publish events when somethinginteresting happens; e.g., change in the code, opening of an issueagainst the code, some other interesting event in the life cycle of thecode, and the like. One non-limiting example of a feed that could behandled with embodiments if the invention is the case where the GitHubsite is configured to publish a stream of events which are of interestto a code developer regarding management of his or her source code. Anembodiment of the invention could be used to write software that wouldmake it easy to manage that feed; in particular, in a serverless system.

For example, consider use of the OpenWhisk serverless event-basedprogramming service to create a simple but useful “bot” for themessaging platform Slack. The following non-limiting example describesan embodiment utilizing the OpenWhisk event-driven programming system(reference is made to the OpenWhisk project, which contains the sourcecode behind IBM Bluemix OpenWhisk). OpenWhisk provides a cloud-nativeevent-based programming system where event handlers are called actions.The following non-limiting example uses OpenWhisk command-linestatements to manipulate actions and feeds. In the example, theapplication, including Whisk actions, waits for events on the GitHubplatform. When a change is made to the code hosted on the GitHubplatform, the application processes the information about the change andpublishes it to a channel on Slack. In such an environment, actions canbe invoked not only from the command line but also automatically. Onepossibility to invoke an action is to call it directly from the code ofanother action. For example, using JavaScript code, an action“gitToSlack” can be created and then invoked when desired.

Consider binding of the git package. To obtain information about changeson GitHub the “github” package can be employed. Inasmuch as someinformation is required, also create an own binding of this package. Inthis non-limiting example, the GitHub username, a repository, and anaccessToken are required:

wsk package bind /whisk.system/github myGit -p username $USERNAME -prepository $REPOSITORY

This will create a package binding called myGit with the pertinentinformation in order to set up a webhook on the repository, which willdeliver information about changes to whisk.

Consider further creating a trigger to listen on GitHub changes.Triggers are a named channel for a stream of events. A trigger can beconfigured with a feed that sets up the source of events; in thisnon-limiting example, GitHub. The action “webhook” is part of the githubpackage and takes a comma-separated list of events as an input. In thisnon-limiting example, it is only desired to know when people pushchanges to the repository.

wsk trigger create myGitTrigger--feed myGit/webhook -p events push

The new trigger is called myGitTrigger. On creating the trigger, executethe feed webhook. It creates a Webhook in GitHub that calls the triggerwhen someone performs a push to the repository. Now all pushes on GitHubwill fire the newly created trigger.

Furthermore with regard to implementation of feeds, FIG. 4 presents anon-limiting custom feed example using a repository hosting service suchas GitHub. As shown at 402, webhooks trigger one or more actions 404.Notification may be of interest, for example, in cases of push, fork,comment, and the like. In a non-limiting example using OpenWhisk feeds,a user binds a package with his or her credentials (parameters):

wsk package bind /whisk.system/github myGit --param username

myGitUser --param repository myGitRepo --param accessToken

aaaaa1111a1a1a1a1a111111aaaaaa1111aa1a1a

The user then creates a trigger (instantiates a stream of events):

wsk trigger create myGitTrigger --feed myGit/webhook --param

events push

Even further, the user creates a rule (hooks a trigger to an action):

wsk rule create R myGitTrigger myAction

The user is thus readily enabled to create a package with a feed, e.g.,/mynamespace/github.

FIG. 5 shows a logical architecture of a github feed service. Anevent-based programming service 502, such as Whisk, is employed and atrigger is created as discussed above. Access to a repository hostingservice 506 such as GitHub is via representational state transfer (REST)API 504. As seen at 508, actions include create, read, update, anddelete. Webhooks 510 are shown in detail in FIG. 4.

FIG. 6 shows an alternative logical architecture of a github feedservice. An event-based programming service 502, such as Whisk, isemployed and a trigger is created as discussed above. Access to arepository hosting service 506 such as GitHub is via a serverless feedaction. As seen at 608, actions include create, read, update, anddelete. Webhooks 510 are shown in detail in FIG. 4.

Referring to FIG. 7, which shows exemplary code, the skilled artisanwill appreciate that a feed action is an OpenWhisk action which managesa feed:

wks trigger create myGitTrigger --feed myGit/webhook -param events push

-> wsk action invoke myGit/webhook

--param events push

--param lifecycleEvent ‘CREATE’

--param triggerName myNamespace/myGitTrigger

--param auth myAuthKey . . .

One pertinent aspect of one or more embodiments is the aspect ofstarting with a system that can execute functions as a building blockand then encode feed management as an instance in the system and use itto plug into the system itself. While feed management itself is known,prior art systems do not teach or suggest a system that can executefunctions in a serverless way with plug-in feed management, in a waythat is extensible, native to the system, and provides a good userexperience.

Advantageously, one or more embodiments are not specific to a mediatype, and/or allow data providers to define policies using a uniformprocess. Indeed, one or more embodiments allow data providers to brokertheir own connections with more than a CREATE feed; the user may DELETE,PAUSE and RESUME the feed.

It should be noted that GitHub is a non-limiting example of a web-basedrepository hosting service and other such services could be used inother embodiments; OpenWhisk is a non-limiting example of a serverlessevent-based programming service and other such services could be used inother embodiments; Slack is a non-limiting example of a messagingplatform and other such platforms could be used in other embodiments;JavaScript is a non-limiting example of an interpreted programminglanguage and other languages could be used in other embodiments; and awebhook, in web development, is a method of augmenting or altering thebehavior of a web page, or web application, with custom callbacks.

One or more embodiments advantageously provide method of establishingexternal feeds between information sources 318 and a cloud platform 302(e.g., cloud computing environment with layers as in FIG. 2 whereinsoftware components of event-based computing system 304 reside as aworkload 96) over a communication network.

Given the discussion thus far, it will be appreciated that, in generalterms, an exemplary method, according to an aspect of the invention,includes receiving, at a cloud platform 302, a class of feed for anexternal feed 320 corresponding to an information source 318 (theexternal feed to produce a corresponding class of events). For example,feed provider 318 provides system 304 on platform 302 with a classcharacterizing its feed 320. The skilled artisan will appreciate that afeed is defined as an abstract data type that produces a “class ofevents.” A further step includes receiving, at the cloud platform, aninstruction 326 corresponding to a create operation for the externalfeed (e.g., from an end user 324 who wishes to consume the feed).

A still further step includes receiving, at the cloud platform, adictionary input 314 corresponding to parameters expected by theinformation source 318. In one or more embodiments, the dictionary inputis provided by the end user 324 (person who desires to consume the feed)and flows to the cloud platform.

Yet a further step includes selecting, at the cloud platform, a handler312 based on the received class of feed and the received createoperation. Recall that in one or more embodiments, the feed provider 318defines a handler 312 for each of the lifecycle events associated forthe feed provider's feed, or alternatively, the feed provider canprovide a single handler, which responds to the various lifecycle eventsas appropriate for each event. Thus, selecting a handler based on thereceived class of feed and the received create operation includes, inthis instance, selecting the handler for the CREATE operation and theparticular class of feed, or selecting the single handler used for allof CREATE, DELETE, PAUSE, and RESUME the particular class of feed andproviding it with whatever parameters it needs to respond appropriatelyto the CREATE event.

Even further steps include transferring, to the handler 312 on the cloudplatform, the input dictionary 314; and generating, at the cloudplatform, a unique destination to receive events for the class ofevents. In a non-limiting example, this generating includes generating aunique Uniform Resource Locator (URL) 316 and the events are receivedvia a call to the uniform resource locator (URL). As noted above, a feedis defined as an abstract data type that produces a “class ofevents”—thus, when setting up a destination, the destination is for aclass of events.

As used herein, a “destination” refers to a web endpoint where theexternal information source can send events; generally a mechanism whichcan listen for events.

Another step includes generating, by the selected handler (say, H₂ outof the M handlers 312) on the cloud platform, a unique request to theinformation source 318 to generate events of the class of feed to theunique destination (e.g. URL 316). Yet further steps include sending, bythe handler on the cloud platform, the request to the information source318; and receiving, at the unique destination (e.g. URL 316), eventsgenerated from the information source 318 responsive to the uniquerequest.

In the step of receiving the class of feed, the class of feed can becontent-based and/or topic-based.

As noted, embodiments are not limited to CREATE operations. Thus, insome instances, further steps include receiving, at the cloud platform302, an instruction corresponding to a delete operation for the externalfeed (e.g. from user 324); selecting, at the cloud platform 302, anappropriate handler 312 based on the received class of feed and thereceived delete operation; running the appropriate handler 312 on thecloud platform 302; and stopping receipt of information from theinformation source 318.

Furthermore in this regard, in some instances, further steps includereceiving, at the cloud platform 302, an instruction corresponding to apause operation for the external feed (e.g. from user 324); selecting,at the cloud platform 302, an appropriate handler 312 based on thereceived class of feed and the received pause operation; running theappropriate handler 312 on the cloud platform 302; and pausing receiptof information from the information source 318. In at least some suchinstances, even further steps include, subsequent to the pausing,receiving, at the cloud platform 302, an instruction corresponding to aresume operation for the external feed (e.g. from user 324); selecting,at the cloud platform 302, another handler 312 based on the receivedclass of feed and the received resume operation; running the otherhandler 312 on the cloud platform 302; and resuming receipt ofinformation from the information source 318. Again, it should be kept inmind that the feed provider 318 may define a handler 312 for each of thelifecycle events associated for the feed provider's feed, oralternatively, the feed provider can provide a single handler, whichresponds to the various lifecycle events as appropriate for each event.

Furthermore, given the discussion thus far, it will be appreciated that,in general terms, an exemplary non-transitory computer readable mediumincludes computer executable instructions which when executed by acomputer cause the computer to perform a method of establishing externalfeeds between information sources and a cloud platform over acommunication network, as set forth above.

Yet further, given the discussion thus far, it will be appreciated that,in general terms, an exemplary system includes a memory; at least oneprocessor, coupled to the memory; and a non-transitory computer readablemedium comprising computer executable instructions which when loadedinto the memory configure the at least one processor to be operative toperform a method of establishing external feeds between informationsources and a cloud platform over a communication network, as set forthabove.

One or more embodiments of the invention, or elements thereof, can beimplemented in the form of an apparatus including a memory and at leastone processor that is coupled to the memory and operative to performexemplary method steps. FIG. 8 depicts a computer system that may beuseful in implementing one or more aspects and/or elements of theinvention, also representative of a cloud computing node according to anembodiment of the present invention. Referring now to FIG. 8, cloudcomputing node 10 is only one example of a suitable cloud computing nodeand is not intended to suggest any limitation as to the scope of use orfunctionality of embodiments of the invention described herein.Regardless, cloud computing node 10 is capable of being implementedand/or performing any of the functionality set forth hereinabove.

In cloud computing node 10 there is a computer system/server 12, whichis operational with numerous other general purpose or special purposecomputing system environments or configurations. Examples of well-knowncomputing systems, environments, and/or configurations that may besuitable for use with computer system/server 12 include, but are notlimited to, personal computer systems, server computer systems, thinclients, thick clients, handheld or laptop devices, multiprocessorsystems, microprocessor-based systems, set top boxes, programmableconsumer electronics, network PCs, minicomputer systems, mainframecomputer systems, and distributed cloud computing environments thatinclude any of the above systems or devices, and the like.

Computer system/server 12 may be described in the general context ofcomputer system executable instructions, such as program modules, beingexecuted by a computer system. Generally, program modules may includeroutines, programs, objects, components, logic, data structures, and soon that perform particular tasks or implement particular abstract datatypes. Computer system/server 12 may be practiced in distributed cloudcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed cloud computing environment, program modules may be locatedin both local and remote computer system storage media including memorystorage devices.

As shown in FIG. 8, computer system/server 12 in cloud computing node 10is shown in the form of a general-purpose computing device. Thecomponents of computer system/server 12 may include, but are not limitedto, one or more processors or processing units 16, a system memory 28,and a bus 18 that couples various system components including systemmemory 28 to processor 16.

Bus 18 represents one or more of any of several types of bus structures,including a memory bus or memory controller, a peripheral bus, anaccelerated graphics port, and a processor or local bus using any of avariety of bus architectures. By way of example, and not limitation,such architectures include Industry Standard Architecture (ISA) bus,Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, and PeripheralComponent Interconnect (PCI) bus.

Computer system/server 12 typically includes a variety of computersystem readable media. Such media may be any available media that isaccessible by computer system/server 12, and it includes both volatileand non-volatile media, removable and non-removable media.

System memory 28 can include computer system readable media in the formof volatile memory, such as random access memory (RAM) 30 and/or cachememory 32. Computer system/server 12 may further include otherremovable/non-removable, volatile/non-volatile computer system storagemedia. By way of example only, storage system 34 can be provided forreading from and writing to a non-removable, non-volatile magnetic media(not shown and typically called a “hard drive”). Although not shown, amagnetic disk drive for reading from and writing to a removable,non-volatile magnetic disk (e.g., a “floppy disk”), and an optical diskdrive for reading from or writing to a removable, non-volatile opticaldisk such as a CD-ROM, DVD-ROM or other optical media can be provided.In such instances, each can be connected to bus 18 by one or more datamedia interfaces. As will be further depicted and described below,memory 28 may include at least one program product having a set (e.g.,at least one) of program modules that are configured to carry out thefunctions of embodiments of the invention.

Program/utility 40, having a set (at least one) of program modules 42,may be stored in memory 28 by way of example, and not limitation, aswell as an operating system, one or more application programs, otherprogram modules, and program data. Each of the operating system, one ormore application programs, other program modules, and program data orsome combination thereof, may include an implementation of a networkingenvironment. Program modules 42 generally carry out the functions and/ormethodologies of embodiments of the invention as described herein.

Computer system/server 12 may also communicate with one or more externaldevices 14 such as a keyboard, a pointing device, a display 24, etc.;one or more devices that enable a user to interact with computersystem/server 12; and/or any devices (e.g., network card, modem, etc.)that enable computer system/server 12 to communicate with one or moreother computing devices. Such communication can occur via Input/Output(I/O) interfaces 22. Still yet, computer system/server 12 cancommunicate with one or more networks such as a local area network(LAN), a general wide area network (WAN), and/or a public network (e.g.,the Internet) via network adapter 20. As depicted, network adapter 20communicates with the other components of computer system/server 12 viabus 18. It should be understood that although not shown, other hardwareand/or software components could be used in conjunction with computersystem/server 12. Examples, include, but are not limited to: microcode,device drivers, redundant processing units, and external disk drivearrays, RAID systems, tape drives, and data archival storage systems,etc.

Thus, one or more embodiments can make use of software running on ageneral purpose computer or workstation. With reference to FIG. 8, suchan implementation might employ, for example, a processor 16, a memory28, and an input/output interface 22 to a display 24 and externaldevice(s) 14 such as a keyboard, a pointing device, or the like. Theterm “processor” as used herein is intended to include any processingdevice, such as, for example, one that includes a CPU (centralprocessing unit) and/or other forms of processing circuitry. Further,the term “processor” may refer to more than one individual processor.The term “memory” is intended to include memory associated with aprocessor or CPU, such as, for example, RAM (random access memory) 30,ROM (read only memory), a fixed memory device (for example, hard drive34), a removable memory device (for example, diskette), a flash memoryand the like. In addition, the phrase “input/output interface” as usedherein, is intended to contemplate an interface to, for example, one ormore mechanisms for inputting data to the processing unit (for example,mouse), and one or more mechanisms for providing results associated withthe processing unit (for example, printer). The processor 16, memory 28,and input/output interface 22 can be interconnected, for example, viabus 18 as part of a data processing unit 12. Suitable interconnections,for example via bus 18, can also be provided to a network interface 20,such as a network card, which can be provided to interface with acomputer network, and to a media interface, such as a diskette or CD-ROMdrive, which can be provided to interface with suitable media.

Accordingly, computer software including instructions or code forperforming the methodologies of the invention, as described herein, maybe stored in one or more of the associated memory devices (for example,ROM, fixed or removable memory) and, when ready to be utilized, loadedin part or in whole (for example, into RAM) and implemented by a CPU.Such software could include, but is not limited to, firmware, residentsoftware, microcode, and the like.

A data processing system suitable for storing and/or executing programcode will include at least one processor 16 coupled directly orindirectly to memory elements 28 through a system bus 18. The memoryelements can include local memory employed during actual implementationof the program code, bulk storage, and cache memories 32 which providetemporary storage of at least some program code in order to reduce thenumber of times code must be retrieved from bulk storage duringimplementation.

Input/output or I/O devices (including but not limited to keyboards,displays, pointing devices, and the like) can be coupled to the systemeither directly or through intervening I/O controllers.

Network adapters 20 may also be coupled to the system to enable the dataprocessing system to become coupled to other data processing systems orremote printers or storage devices through intervening private or publicnetworks. Modems, cable modem and Ethernet cards are just a few of thecurrently available types of network adapters.

As used herein, including the claims, a “server” includes a physicaldata processing system (for example, system 12 as shown in FIG. 8)running a server program. It will be understood that such a physicalserver may or may not include a display and keyboard. Note that whileFIG. 8 shows is representative of a server, it is also representative ofa variety of other computer systems, and some embodiments of theinvention are implemented in a serverless fashion, as discussed herein.

One or more embodiments can be at least partially implemented in thecontext of a cloud or virtual machine environment, although this isexemplary and non-limiting. Reference is made back to FIGS. 1-2 andaccompanying text. Consider, e.g., a cloud computing environment withlayers as in FIG. 2 wherein software components of event-based computingsystem 304 reside as a workload 96 in layer 90.

It should be noted that any of the methods described herein can includean additional step of providing a system comprising distinct softwaremodules embodied on a computer readable storage medium; the modules caninclude, for example, any or all of the appropriate elements depicted inthe block diagrams and/or described herein; by way of example and notlimitation, any one, some or all of the modules/blocks and orsub-modules/sub-blocks described (e.g., in FIGS. 3, 5, and 6). Themethod steps can then be carried out using the distinct software modulesand/or sub-modules of the system, as described above, executing on oneor more hardware processors such as 16. Further, a computer programproduct can include a computer-readable storage medium with code adaptedto be implemented to carry out one or more method steps describedherein, including the provision of the system with the distinct softwaremodules.

One example of user interface that could be employed in some cases ishypertext markup language (HTML) code served out by a server or thelike, to a browser of a computing device of a user. The HTML is parsedby the browser on the user's computing device to create a graphical userinterface (GUI). Other types of user interface can be employed. Someembodiments can employ a command line interface.

Exemplary System and Article of Manufacture Details

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, configuration data for integrated circuitry, oreither source code or object code written in any combination of one ormore programming languages, including an object oriented programminglanguage such as Smalltalk, C++, or the like, and procedural programminglanguages, such as the “C” programming language or similar programminglanguages. The computer readable program instructions may executeentirely on the user's computer, partly on the user's computer, as astand-alone software package, partly on the user's computer and partlyon a remote computer or entirely on the remote computer or server. Inthe latter scenario, the remote computer may be connected to the user'scomputer through any type of network, including a local area network(LAN) or a wide area network (WAN), or the connection may be made to anexternal computer (for example, through the Internet using an InternetService Provider). In some embodiments, electronic circuitry including,for example, programmable logic circuitry, field-programmable gatearrays (FPGA), or programmable logic arrays (PLA) may execute thecomputer readable program instructions by utilizing state information ofthe computer readable program instructions to personalize the electroniccircuitry, in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the blocks may occur out of theorder noted in the Figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the describedembodiments. The terminology used herein was chosen to best explain theprinciples of the embodiments, the practical application or technicalimprovement over technologies found in the marketplace, or to enableothers of ordinary skill in the art to understand the embodimentsdisclosed herein.

What is claimed is:
 1. A method comprising: receiving, at a cloudplatform, a class of feed for an external feed corresponding to aninformation source, said external feed to produce a corresponding classof events, said class of feed being based on a model; receiving, at saidcloud platform, an instruction corresponding to a create operation forsaid external feed; receiving, at said cloud platform, inputcorresponding to parameters expected by said information source;selecting, at said cloud platform, a handler from a plurality ofhandlers based on said received class of feed and said received createoperation, each handler being responsive to lifecycle events on saidexternal feed transparent to a user; transferring, to said handler onsaid cloud platform, said input; generating, at said cloud platform, aunique destination to receive events for said class of events;generating, by said handler on said cloud platform, a unique request tosaid information source to generate events of said class of feed to saidunique destination transparent to said user; sending, by said handler onsaid cloud platform, said request to said information source; andreceiving, at said unique destination, events generated from saidinformation source responsive to said unique request.
 2. The method ofclaim 1, wherein in said step of receiving said class of feed, saidclass of feed is content-based.
 3. The method of claim 1, wherein insaid step of receiving said class of feed, said class of feed istopic-based.
 4. The method of claim 1, further comprising: receiving, atsaid cloud platform, an instruction corresponding to a delete operationfor said external feed; selecting, at said cloud platform, anappropriate handler based on said received class of feed and saidreceived delete operation; running said appropriate handler on saidcloud platform; and stopping receipt of information from saidinformation source.
 5. The method of claim 1, further comprising:receiving, at said cloud platform, an instruction corresponding to apause operation for said external feed; selecting, at said cloudplatform, an appropriate handler based on said received class of feedand said received pause operation; running said appropriate handler onsaid cloud platform; and pausing receipt of information from saidinformation source.
 6. The method of claim 5, further comprising,subsequent to said pausing: receiving, at said cloud platform, aninstruction corresponding to a resume operation for said external feed;selecting, at said cloud platform, another handler based on saidreceived class of feed and said received resume operation; running saidother handler on said cloud platform; and resuming receipt ofinformation from said information source.
 7. The method of claim 1,wherein said generating of said unique destination comprises generatinga unique uniform resource locator (URL) and said events are received viaa call to said uniform resource locator (URL).
 8. A non-transitorycomputer readable medium comprising computer executable instructionswhich when executed by a computer cause the computer to perform themethod of: receiving, at a cloud platform, a class of feed for anexternal feed corresponding to an information source, said external feedto produce a corresponding class of events, said class of feed beingbased on a model; receiving, at said cloud platform, an instructioncorresponding to a create operation for said external feed; receiving,at said cloud platform, input corresponding to parameters expected bysaid information source; selecting, at said cloud platform, a handlerfrom a plurality of handlers based on said received class of feed andsaid received create operation, each handler being responsive tolifecycle events on said external feed transparent to a user;transferring, to said handler on said cloud platform, said input;generating, at said cloud platform, a unique destination to receiveevents for said class of events transparent to said user; generating, bysaid handler on said cloud platform, a unique request to saidinformation source to generate events of said class of feed to saidunique destination; sending, by said handler on said cloud platform,said request to said information source; and receiving, at said uniquedestination, events generated from said information source responsive tosaid unique request.
 9. The non-transitory computer readable medium ofclaim 8, wherein in said step of receiving said class of feed, saidclass of feed is content-based.
 10. The non-transitory computer readablemedium of claim 8, wherein in said step of receiving said class of feed,said class of feed is topic-based.
 11. The non-transitory computerreadable medium of claim 8, further comprising: receiving, at said cloudplatform, an instruction corresponding to a delete operation for saidexternal feed; selecting, at said cloud platform, an appropriate handlerbased on said received class of feed and said received delete operation;running said appropriate handler on said cloud platform; and stoppingreceipt of information from said information source.
 12. Thenon-transitory computer readable medium of claim 8, further comprising:receiving, at said cloud platform, an instruction corresponding to apause operation for said external feed; selecting, at said cloudplatform, an appropriate handler based on said received class of feedand said received pause operation; running said appropriate handler onsaid cloud platform; and pausing receipt of information from saidinformation source.
 13. The non-transitory computer readable medium ofclaim 12, further comprising, subsequent to said pausing: receiving, atsaid cloud platform, an instruction corresponding to a resume operationfor said external feed; selecting, at said cloud platform, anotherhandler based on said received class of feed and said received resumeoperation; running said other handler on said cloud platform; andresuming receipt of information from said information source.
 14. Thenon-transitory computer readable medium of claim 8, wherein saidgenerating of said unique destination comprises generating a uniqueuniform resource locator (URL) and said events are received via a callto said uniform resource locator (URL).
 15. An apparatus comprising: amemory; at least one processor, coupled to said memory, and anon-transitory computer readable medium comprising computer executableinstructions which when loaded into said memory configure said at leastone processor to be operative to: receive, at a cloud platform, a classof feed for an external feed corresponding to an information source,said external feed to produce a corresponding class of events, saidclass of feed being based on a model; receive, at said cloud platform,an instruction corresponding to a create operation for said externalfeed; receive, at said cloud platform, input corresponding to parametersexpected by said information source; select, at said cloud platform, ahandler from a plurality of handlers based on said received class offeed and said received create operation, each handler being responsiveto lifecycle events on said external feed transparent to a user;transfer, to said handler on said cloud platform, said input; generate,at said cloud platform, a unique destination to receive events for saidclass of events; generate, by said handler on said cloud platform, aunique request to said information source to generate events of saidclass of feed to said unique destination transparent to said user; send,by said handler on said cloud platform, said request to said informationsource; and receive, at said unique destination, events generated fromsaid information source responsive to said unique request.
 16. Theapparatus of claim 15, wherein said class of feed is content-based. 17.The apparatus of claim 15, wherein said class of feed is topic-based.18. The apparatus of claim 15, wherein said computer executableinstructions, when loaded into said memory, further configure said atleast one processor to be operative to: receive, at said cloud platform,an instruction corresponding to a delete operation for said externalfeed; select, at said cloud platform, an appropriate handler based onsaid received class of feed and said received delete operation; run saidappropriate handler on said cloud platform; and stop receipt ofinformation from said information source.
 19. The apparatus of claim 15,wherein said computer executable instructions, when loaded into saidmemory, further configure said at least one processor to be operativeto: receive, at said cloud platform, an instruction corresponding to apause operation for said external feed; select, at said cloud platform,an appropriate handler based on said received class of feed and saidreceived pause operation; run said appropriate handler on said cloudplatform; pause receipt of information from said information source;subsequent to said pausing, receive, at said cloud platform, aninstruction corresponding to a resume operation for said external feed;subsequent to said pausing, select, at said cloud platform, anotherhandler based on said received class of feed and said received resumeoperation; subsequent to said pausing, run said other handler on saidcloud platform; and subsequent to said pausing, resume receipt ofinformation from said information source.
 20. The apparatus of claim 15,wherein said computer executable instructions, when loaded into saidmemory, configure said at least one processor such that said generatingof said unique destination comprises generating a unique uniformresource locator (URL) and said events are received via a call to saiduniform resource locator (URL).